Issue breakdown

Prior to this PR, our approach was to invalidate variables and attempt to refetch existing ones based on known container references. This method proved problematic because all objects (stack frames, scopes, variables) should be considered stale after an object modification.

This was the primary reason why, when trying to refetch variables with current container references, we often failed to see nested variables appear. The issue was twofold: not only did reusing stale container references prevent nested variables from showing up, but we also used the variable reference as unique id to determine what variable to show, which changes when an object was modified or when moving to the next frame.

To address this issue, I've implemented two key changes:

1. I modified the unique ID used to determine which entry to display. Now, we only use the variable's depth and name, as these two attributes remain constant over time.

2. I altered the variable fetching mechanism. We now retrieve all previously opened variables, eliminating the need to repeatedly click open the same variable during step debugging.

These changes should significantly improve the reliability and user experience of the debugging process.

Example

Before

After